Upgrade FreeRADIUS
The upgrade scenarios will be handled by the deployment shell script FreeRADIUSv3.sh by itself. No input is required.
Earlier FreeRADIUS releases before v3.0 had following three components:
-
FreeRADIUS Agent
-
FreeRADIUS Updater
-
FreeRADIUS Server
For the agent solution to work, all three components needed to be installed and configured. Now, the agent is deployed using a simple shell script. Executing the script will confirm some details from the end user, and will help in quick, hassle-free agent upgradation.
Upgrading SafeNet Agent for FreeRADIUS 1.X with FreeRADIUS Server 2.X
Follow the steps to upgrade the agent with FreeRADIUS Server 2.X installations:
-
Execute the
FreeRADIUSv3.shshell script from the package. -
The shell script will stop the RADIUS Daemon, if it finds the agent.
FreeRadius Agent for Radius Server 2.X found. Stopping the Radius daemon… -
If found, the shell script will then stop the FreeRADIUS Updater service.
FreeRadius Updater for Radius Server 2.X found. Stopping the FreeRadius Updater Service… Stopping the freerad_updaterservice (via systemctl): [ OK ]The above two steps check for prerequisites. If the prerequisites are met, the FreeRADIUS container will be deployed.
-
After the container has been deployed successfully, the script will remove the previous installations.
New container deployed successfully. Checking old installations… -
The script also removes the installed RPMs packages of FreeRADIUS Agent and FreeRADIUS Updater.
Uninstalling the FreeRadius Agent and Free Radius Updater RPMs… Uninstallation completed.
Upgrading SafeNet Agent for FreeRADIUS with FreeRADIUS Server 3.X
Follow the steps to upgrade the agent with FreeRADIUS Server 3.X installations, if in addition to FreeRADIUS Agent and FreeRADIUS Updater, a FreeRADIUS container is already present.
-
Execute the
FreeRADIUSv3.shshell script from the package. -
The shell script will check if a FreeRADIUS container already exists. If it exists, the script stops and renames the existing container to FreeRADIUSv3_Old. The renaming is done to deploy a new FreeRADIUS container (FreeRADIUSv3) as containers with same names cannot be deployed.
Docker container for RADIUS Server 3.x found. Stopping old container to deploy new FreeRADIUS container… FreeRADIUSv3 Renaming old container to ‘FreeRADIUS_Old’…The above step checks for the additional prerequisite. If the prerequisite is met, the FreeRADIUS container will be deployed.
-
After the container has been deployed successfully, the script will remove the previous installations.
New container deployed successfully. Checking old installations… -
The script also removes the old FreeRADIUS container.
New container deployed successfully. Checking old installations… Uninstalling the old container… FreeRADIUSv3_OldTo ensure uninterrupted access to the FreeRADIUS container (after installation), execute the Startup Script.